Wolters Kluwer CCH® SureTax®

    Show / Hide Table of Contents

    Batch Upload API

    POST Upload

    POST Upload

    Overview

    The Upload API endpoint is designed to facilitate the process of uploading files into the SureTax system. This endpoint requires the inclusion of a specific header called X-Import-Type to specify the type of file being uploaded. In the body of the API request, the following parameters need to be included:

    1. legalEntityCode: This parameter represents the code or identifier for the legal entity associated with the uploaded file.

    2. DatayearMonth: This parameter specifies the year and month associated with the data being uploaded.

    3. filelayoutversion: This parameter indicates the version or format of the file being uploaded.

    It ensures that the SureTax system can correctly interpret and process the data within the file. By utilizing this upload API endpoint, users can seamlessly transfer their files into the SureTax system.

    OperationId: POST Upload

    Authorization Method(s): OAuth

    Verb: POST

    End Point: /api/v1/Batch/Upload


    Request Body
    Request Model
    Display NameField NameField Type
    File Content *fileContentstring
    Request Data *requestDataRequestDataDetails
    RequestDataDetails
    Display NameField NameField Type
    Legal Entity Code *legalEntityCodestring
    File Layout Version *fileLayoutVersionstring
    Data Year Month *dataYearMonthstring
    Compliance Year Month complianceYearMonthstring
    Configuration Name configurationNamestring

    Example Request

    The following is an json request for this operation.

    {
      "legalEntityCode": "B000112005",
      "fileLayoutVersion": "1.0",
      "dataYearMonth": "202501"
    }

    Request Headers
    Many of the request headers listed below are designed to enhance traceability and provide supplementary information, allowing our team to efficiently identify and assess your API requests. Including these headers offers numerous benefits: they improve debugging and support by facilitating quick issue identification, enhance security through secure access and traceable actions, ensure accurate request tracking for thorough auditing, support better client management for compatibility, enable localization and personalization for tailored responses, and optimize business processes with clearer operation definitions. For implementation examples, please refer to our SDKs, which provide comprehensive guidance and practical integrations.

    Display String Field Name Field Type
    X-request-id* x-request-id string
    X-import-type* x-import-type string
    *Mandatory parameter

    Response Codes
    Response codes in an API indicate the outcome of a request. They are three-digit numbers returned by the server to help the client understand if the request was successful, encountered an error, or needs further action. This operation has the following possible responses.

    code description
    202 The API responds with this code to indicate that the data was sent successfully.
    400 Bad Request - The server could not process the request due to invalid input or missing required parameters.
    401 Unauthorized: The user's authentication is not valid.
    500 Internal Server Error - An unexpected error occurred on the server while processing the request.




    No file chosen

    Enter Environment Credentials








    Wolters Kluwer Product Name - Page anchor links toWolters Kluwer Product Name - Page anchor links to
    © Wolters Kluwer and/or its affiliates. All rights reserved.